Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 74aef008d4c02812abcbae99616119b3802c4e06f0c997242f43520eb4929186

Tx prefix hash: e36f57105e41cbce23453cf11e6e6e5776b4fa4f19dd2fccb45c0e0ced2ccd59
Tx public key: 9ba431a343f0edb6b015f14330941de7c3ca723d49f12d31d9e5eb26de189797
Timestamp: 1714092099 Timestamp [UCT]: 2024-04-26 00:41:39 Age [y:d:h:m:s]: 00:256:13:50:40
Block: 1008565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183663 RingCT/type: yes/0
Extra: 019ba431a343f0edb6b015f14330941de7c3ca723d49f12d31d9e5eb26de18979702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 005bbe5a59f566b323a3f5aedc227df9491bb23ac03118b826b22d9368996e58 0.600000000000 1470037 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1008575, "vin": [ { "gen": { "height": 1008565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "005bbe5a59f566b323a3f5aedc227df9491bb23ac03118b826b22d9368996e58" } } ], "extra": [ 1, 155, 164, 49, 163, 67, 240, 237, 182, 176, 21, 241, 67, 48, 148, 29, 231, 195, 202, 114, 61, 73, 241, 45, 49, 217, 229, 235, 38, 222, 24, 151, 151, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8