Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd05a92e42d2b047d76a141b0547bb39ad79ff1a2d5416ec2c79e249f40debcc

Tx prefix hash: 9279013b733122c7e8fe44ab80e5759b4491642b32e99d58b29983e7d7190642
Tx public key: 3edeb7b99600e7ac4e42d6dc7d264714e4b4003249246c5a0e0ede8a07673498
Timestamp: 1723578836 Timestamp [UCT]: 2024-08-13 19:53:56 Age [y:d:h:m:s]: 00:234:05:58:45
Block: 1087223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167296 RingCT/type: yes/0
Extra: 013edeb7b99600e7ac4e42d6dc7d264714e4b4003249246c5a0e0ede8a07673498021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22d2caf331f174c1ad21e4638c5fcb8f135dd1b5038096af3ecd8c95c1d3cc6f 0.600000000000 1561828 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": 1087233, "vin": [ { "gen": { "height": 1087223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22d2caf331f174c1ad21e4638c5fcb8f135dd1b5038096af3ecd8c95c1d3cc6f" } } ], "extra": [ 1, 62, 222, 183, 185, 150, 0, 231, 172, 78, 66, 214, 220, 125, 38, 71, 20, 228, 180, 0, 50, 73, 36, 108, 90, 14, 14, 222, 138, 7, 103, 52, 152, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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