Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9123394be07d9bf7647d6d706aef26f811b4acbbdde139c5ad781cded5109752

Tx prefix hash: 40f5ad12061df26f49e46046704271d3cf2b0c6c37c99e5bc2524851866ee547
Tx public key: 49a96f73869a3103b58d16317d4ecec3c293de978f7711c4e944e58ef6bf3ea6
Timestamp: 1723879225 Timestamp [UCT]: 2024-08-17 07:20:25 Age [y:d:h:m:s]: 00:191:02:28:30
Block: 1089728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136410 RingCT/type: yes/0
Extra: 0149a96f73869a3103b58d16317d4ecec3c293de978f7711c4e944e58ef6bf3ea6021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52e5337f13c15791b781b5a67d081c929a212dff8bf01db9593cdf6d4f2a8cc5 0.600000000000 1564351 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": 1089738, "vin": [ { "gen": { "height": 1089728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52e5337f13c15791b781b5a67d081c929a212dff8bf01db9593cdf6d4f2a8cc5" } } ], "extra": [ 1, 73, 169, 111, 115, 134, 154, 49, 3, 181, 141, 22, 49, 125, 78, 206, 195, 194, 147, 222, 151, 143, 119, 17, 196, 233, 68, 229, 142, 246, 191, 62, 166, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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