Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314660a715514b9c28a1ce4ae0930ef29f3a89e3b14aa30f9713ca2958c39b15

Tx prefix hash: 11270222d2e2fa6200534679f59808614ab90a9a1394d7a5e0eea44c98b1f468
Tx public key: 02d84d0f10a100867271c964536ef35f75c429a6e79cb4a80a3b3b1b0ff99c96
Timestamp: 1712621933 Timestamp [UCT]: 2024-04-09 00:18:53 Age [y:d:h:m:s]: 01:004:16:50:09
Block: 996358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264349 RingCT/type: yes/0
Extra: 0102d84d0f10a100867271c964536ef35f75c429a6e79cb4a80a3b3b1b0ff99c9602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60f170c96f52e22e961e21afca1619265933959ebc3f7996bf91299609d34033 0.600000000000 1456776 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": 996368, "vin": [ { "gen": { "height": 996358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60f170c96f52e22e961e21afca1619265933959ebc3f7996bf91299609d34033" } } ], "extra": [ 1, 2, 216, 77, 15, 16, 161, 0, 134, 114, 113, 201, 100, 83, 110, 243, 95, 117, 196, 41, 166, 231, 156, 180, 168, 10, 59, 59, 27, 15, 249, 156, 150, 2, 17, 0, 0, 0, 1, 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