Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d3843a7d0b4d12f79bdcb7e06029b7494e6a7b7f5b64fef86f78a7dd6ab20f5

Tx prefix hash: d2d97feb03200837ee25e53a95f3c299c505acb9b7f20a20246d032a71ed7342
Tx public key: 62d08abe575594fdce07808f5358ab33ea7a15e5853e98ed808c5654adaaa900
Timestamp: 1717392565 Timestamp [UCT]: 2024-06-03 05:29:25 Age [y:d:h:m:s]: 00:237:02:21:55
Block: 1035953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169624 RingCT/type: yes/0
Extra: 0162d08abe575594fdce07808f5358ab33ea7a15e5853e98ed808c5654adaaa90002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f84d0d952a69b4d09b608aec8f3434126b2c45ed585cc32858f3e949d0df8e 0.600000000000 1504478 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": 1035963, "vin": [ { "gen": { "height": 1035953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f84d0d952a69b4d09b608aec8f3434126b2c45ed585cc32858f3e949d0df8e" } } ], "extra": [ 1, 98, 208, 138, 190, 87, 85, 148, 253, 206, 7, 128, 143, 83, 88, 171, 51, 234, 122, 21, 229, 133, 62, 152, 237, 128, 140, 86, 84, 173, 170, 169, 0, 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