Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39c2c5064293706e6b5cdb0a667fdfd6539c608a3884bfa6974a91fd7a0e70e9

Tx prefix hash: ec8c605e13e66907647ab43d715a1782a2284a7b7b107b0bae37245744b2ac33
Tx public key: 6b0a857e2c9ace032a06751f33191027b55503664093790ff6ee3a897a5519ea
Timestamp: 1676199151 Timestamp [UCT]: 2023-02-12 10:52:31 Age [y:d:h:m:s]: 02:101:22:45:52
Block: 695311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594506 RingCT/type: yes/0
Extra: 016b0a857e2c9ace032a06751f33191027b55503664093790ff6ee3a897a5519ea02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.048919373000 dcy

stealth address amount amount idx
00: f671cf9a213e47b82245245d6b6fad5985a93a7da0865711655dd49fb2436d15 3.048919373000 1138264 of 0

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": 695321, "vin": [ { "gen": { "height": 695311 } } ], "vout": [ { "amount": 3048919373, "target": { "key": "f671cf9a213e47b82245245d6b6fad5985a93a7da0865711655dd49fb2436d15" } } ], "extra": [ 1, 107, 10, 133, 126, 44, 154, 206, 3, 42, 6, 117, 31, 51, 25, 16, 39, 181, 85, 3, 102, 64, 147, 121, 15, 246, 238, 58, 137, 122, 85, 25, 234, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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