Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80798297863065f0af99e35272f69507d2efa34b48264f7d7e8087975cacb0f7

Tx prefix hash: 2f235121fc311423f28402bcb8ad79654a2c950bdc83a8da2b517eeda3ee0d4a
Tx public key: c571ae5e452209a13e823cae60055fd6bf08dd59da09d3f7d00c3915bdc75ae8
Timestamp: 1736087011 Timestamp [UCT]: 2025-01-05 14:23:31 Age [y:d:h:m:s]: 00:163:03:59:54
Block: 1190796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116318 RingCT/type: yes/0
Extra: 01c571ae5e452209a13e823cae60055fd6bf08dd59da09d3f7d00c3915bdc75ae802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec930b1518c344a738b8d97a5e4a9e4b104e1ad7920509c39af38e92786c047 0.600000000000 1677315 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": 1190806, "vin": [ { "gen": { "height": 1190796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec930b1518c344a738b8d97a5e4a9e4b104e1ad7920509c39af38e92786c047" } } ], "extra": [ 1, 197, 113, 174, 94, 69, 34, 9, 161, 62, 130, 60, 174, 96, 5, 95, 214, 191, 8, 221, 89, 218, 9, 211, 247, 208, 12, 57, 21, 189, 199, 90, 232, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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