Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 501ad2627075174e9223659468245d8ed4784f0b7fecf067219f264767b0da81

Tx prefix hash: 5864b84d968aee07f16cc67620abb5df612f566fea04d1236c43ebf3d6f33b72
Tx public key: 71b4c243b0660ebb56ba81a2cc0b8671f408963137eb2c9806e4efb2f5cfa07d
Timestamp: 1706435848 Timestamp [UCT]: 2024-01-28 09:57:28 Age [y:d:h:m:s]: 01:308:16:08:36
Block: 945079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479444 RingCT/type: yes/0
Extra: 0171b4c243b0660ebb56ba81a2cc0b8671f408963137eb2c9806e4efb2f5cfa07d02110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a79d53c4c6d3c4dbe12d216ab50c5a9c08ee7e076292968449ebc9a70f54123 0.600000000000 1403387 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": 945089, "vin": [ { "gen": { "height": 945079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a79d53c4c6d3c4dbe12d216ab50c5a9c08ee7e076292968449ebc9a70f54123" } } ], "extra": [ 1, 113, 180, 194, 67, 176, 102, 14, 187, 86, 186, 129, 162, 204, 11, 134, 113, 244, 8, 150, 49, 55, 235, 44, 152, 6, 228, 239, 178, 245, 207, 160, 125, 2, 17, 0, 0, 0, 18, 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