Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 218692d0d8f777c1cb98bc864b8bcc8404e39ccc4074c60ac6bcc01930647bdf

Tx prefix hash: f94d7b79f9f23f16d17b13d012a95ca43607937d6035c4d7a4abf5fe99255d16
Tx public key: d983889421dbf7b17600a0c7f8405f5cf71bf5c526617a3e96048e8695f3cc73
Timestamp: 1728830573 Timestamp [UCT]: 2024-10-13 14:42:53 Age [y:d:h:m:s]: 00:172:15:36:45
Block: 1130768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123173 RingCT/type: yes/0
Extra: 01d983889421dbf7b17600a0c7f8405f5cf71bf5c526617a3e96048e8695f3cc7302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47983d72d9fa23b66647724b47b4ddc40bd6a4cb7644f46ca9ed9ec05bf1b0bc 0.600000000000 1613647 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": 1130778, "vin": [ { "gen": { "height": 1130768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47983d72d9fa23b66647724b47b4ddc40bd6a4cb7644f46ca9ed9ec05bf1b0bc" } } ], "extra": [ 1, 217, 131, 136, 148, 33, 219, 247, 177, 118, 0, 160, 199, 248, 64, 95, 92, 247, 27, 245, 197, 38, 97, 122, 62, 150, 4, 142, 134, 149, 243, 204, 115, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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