Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d373c4059d186b3e094ee78a3aaec6f34c4218f9a6036c2fde3aa6508e7cb86

Tx prefix hash: db7d5abaf68c8860a5b16daf17351e04a6c468846c3ebb0e362b5472e07cfabf
Tx public key: b9e5a893099fefcf57378943bfc968370960f963cbcca9c5eaf39c73c3a4790a
Timestamp: 1709980081 Timestamp [UCT]: 2024-03-09 10:28:01 Age [y:d:h:m:s]: 01:244:16:21:42
Block: 974501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433571 RingCT/type: yes/0
Extra: 01b9e5a893099fefcf57378943bfc968370960f963cbcca9c5eaf39c73c3a4790a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0ea35e32cca8addca54ce3476d5ecf087ddfefccd8a45297fdd746a65338126 0.600000000000 1434460 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": 974511, "vin": [ { "gen": { "height": 974501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ea35e32cca8addca54ce3476d5ecf087ddfefccd8a45297fdd746a65338126" } } ], "extra": [ 1, 185, 229, 168, 147, 9, 159, 239, 207, 87, 55, 137, 67, 191, 201, 104, 55, 9, 96, 249, 99, 203, 204, 169, 197, 234, 243, 156, 115, 195, 164, 121, 10, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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