Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a748f2064f8d4a849845c0664ae70ee4339627e50b2e74c4fb5c03a923e76b7d

Tx prefix hash: 644f8c696bc89b88320a6fe5b63876d75abb6cc4a3fc780d337b56209c0bbf6a
Tx public key: 7aa3501164dfebf78e04b7f432b1c6c58af920a33d0905b8a26f6987f8a9c0b3
Timestamp: 1710609266 Timestamp [UCT]: 2024-03-16 17:14:26 Age [y:d:h:m:s]: 01:237:14:23:24
Block: 979721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428497 RingCT/type: yes/0
Extra: 017aa3501164dfebf78e04b7f432b1c6c58af920a33d0905b8a26f6987f8a9c0b30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae1369c14b580675d3128ff18fee4caa3020463371f1c4f89a57c8570dce81d 0.600000000000 1439772 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": 979731, "vin": [ { "gen": { "height": 979721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae1369c14b580675d3128ff18fee4caa3020463371f1c4f89a57c8570dce81d" } } ], "extra": [ 1, 122, 163, 80, 17, 100, 223, 235, 247, 142, 4, 183, 244, 50, 177, 198, 197, 138, 249, 32, 163, 61, 9, 5, 184, 162, 111, 105, 135, 248, 169, 192, 179, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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