Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5874773d32ab12acc0540839763b4a72d48ed691b20a51d4f51b76da1e6ea239

Tx prefix hash: 67f76861972288611fe2700c12b76f0e8da94696c2af8a0610a331fa25e37c25
Tx public key: 9a9aeb90768dc30e862810386a7f6e11f7dee6fde674d2f1efa4dc8c6db992e9
Timestamp: 1734979480 Timestamp [UCT]: 2024-12-23 18:44:40 Age [y:d:h:m:s]: 00:334:23:17:41
Block: 1181644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236915 RingCT/type: yes/0
Extra: 019a9aeb90768dc30e862810386a7f6e11f7dee6fde674d2f1efa4dc8c6db992e90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4413e8cd167b6f875a3bbd860ecdb0b859295bfde9090bbb57cef1e7fd4b1d9d 0.600000000000 1668069 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": 1181654, "vin": [ { "gen": { "height": 1181644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4413e8cd167b6f875a3bbd860ecdb0b859295bfde9090bbb57cef1e7fd4b1d9d" } } ], "extra": [ 1, 154, 154, 235, 144, 118, 141, 195, 14, 134, 40, 16, 56, 106, 127, 110, 17, 247, 222, 230, 253, 230, 116, 210, 241, 239, 164, 220, 140, 109, 185, 146, 233, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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