Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71739c11b954dd3796ba308a865fc48df0998b8ecef8ff7d1efd892eb7ee4527

Tx prefix hash: 0f349d2ce959257f3a74c772d31c482eb2f2ea668f28ef60e860c82cff11b48b
Tx public key: 6a9ef206e42b133196ab7784c3e85f187d1397c22b7ee909a777a8dbf940ea12
Timestamp: 1709972287 Timestamp [UCT]: 2024-03-09 08:18:07 Age [y:d:h:m:s]: 00:293:20:58:48
Block: 974433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210352 RingCT/type: yes/0
Extra: 016a9ef206e42b133196ab7784c3e85f187d1397c22b7ee909a777a8dbf940ea1202110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a6df0848c807318eb0b0cb6a9eca7056475f5bc97911bcd4441ab5057d96f6 0.600000000000 1434388 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": 974443, "vin": [ { "gen": { "height": 974433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a6df0848c807318eb0b0cb6a9eca7056475f5bc97911bcd4441ab5057d96f6" } } ], "extra": [ 1, 106, 158, 242, 6, 228, 43, 19, 49, 150, 171, 119, 132, 195, 232, 95, 24, 125, 19, 151, 194, 43, 126, 233, 9, 167, 119, 168, 219, 249, 64, 234, 18, 2, 17, 0, 0, 0, 7, 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