Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 174049ad87dce96ef424aba8f618b81b7e47c593ece3cf1b961901fd7c9438b8

Tx prefix hash: 52631ff745264d74ae09b0b7378462e76b93f8ccee753a1a532ce4c59c959702
Tx public key: cf1c47c56c99a27446a605cff2e22fefe0e67b735903c761a0bcaea0d92d8a54
Timestamp: 1719156023 Timestamp [UCT]: 2024-06-23 15:20:23 Age [y:d:h:m:s]: 00:266:21:11:14
Block: 1050536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190733 RingCT/type: yes/0
Extra: 01cf1c47c56c99a27446a605cff2e22fefe0e67b735903c761a0bcaea0d92d8a5402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e263e91fdbc7bdf7fbad01c10d1109ac04766c722ff74bb6e7b4ee2d6cb36c4 0.600000000000 1520711 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": 1050546, "vin": [ { "gen": { "height": 1050536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e263e91fdbc7bdf7fbad01c10d1109ac04766c722ff74bb6e7b4ee2d6cb36c4" } } ], "extra": [ 1, 207, 28, 71, 197, 108, 153, 162, 116, 70, 166, 5, 207, 242, 226, 47, 239, 224, 230, 123, 115, 89, 3, 199, 97, 160, 188, 174, 160, 217, 45, 138, 84, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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