Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ecbc9a5c78a6afd00768c13301c817e7660bc8ac9595d03519ff3c1d3a8e22

Tx prefix hash: 6516e3cfcb1cf98eb4496498b22403e28af74b019b64eaa0f608256334759671
Tx public key: ee87b9441df6aae85c791db951e721de78cd19c294e20524e8bf811bec8cad10
Timestamp: 1716269373 Timestamp [UCT]: 2024-05-21 05:29:33 Age [y:d:h:m:s]: 00:363:01:43:31
Block: 1026642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259512 RingCT/type: yes/0
Extra: 01ee87b9441df6aae85c791db951e721de78cd19c294e20524e8bf811bec8cad1002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dfdae9843c06c1c87aec7a444813bcd253fe836b7b957a09e55cb09daf1516b 0.600000000000 1493835 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": 1026652, "vin": [ { "gen": { "height": 1026642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dfdae9843c06c1c87aec7a444813bcd253fe836b7b957a09e55cb09daf1516b" } } ], "extra": [ 1, 238, 135, 185, 68, 29, 246, 170, 232, 92, 121, 29, 185, 81, 231, 33, 222, 120, 205, 25, 194, 148, 226, 5, 36, 232, 191, 129, 27, 236, 140, 173, 16, 2, 17, 0, 0, 0, 2, 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