Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4190294ecb1c19ab45881a66ca4d13e5782e247de2b90f1bb4e1ea26594e215f

Tx prefix hash: e5d15f2fc26036bcc99fbc4ab62de0bec2e0e873d31543e551a7cb7073fe6288
Tx public key: d70573fd9cad591e4c75a910b07c59c001d009ef088e5de5e65dab1df99661cb
Timestamp: 1713919802 Timestamp [UCT]: 2024-04-24 00:50:02 Age [y:d:h:m:s]: 01:034:09:47:49
Block: 1007142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285565 RingCT/type: yes/0
Extra: 01d70573fd9cad591e4c75a910b07c59c001d009ef088e5de5e65dab1df99661cb02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c57368fb390e98df203ee18d79bf11f5d859895995c7bc69b2e5815e11f6eb8 0.600000000000 1468388 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": 1007152, "vin": [ { "gen": { "height": 1007142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c57368fb390e98df203ee18d79bf11f5d859895995c7bc69b2e5815e11f6eb8" } } ], "extra": [ 1, 215, 5, 115, 253, 156, 173, 89, 30, 76, 117, 169, 16, 176, 124, 89, 192, 1, 208, 9, 239, 8, 142, 93, 229, 230, 93, 171, 29, 249, 150, 97, 203, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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