Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aa347c833d9e036f3f261066e73c45a4a962345d03ad6fbe0a10b50fdaad533

Tx prefix hash: fa96c05276f7f77b8da7308a5434bd28fc4738294db197d28c559b9377b2085c
Tx public key: 2379ca47f370fca2bbb0d841c480221e04c7b13ff25e35eefdc4668e8aaeb27c
Timestamp: 1717641394 Timestamp [UCT]: 2024-06-06 02:36:34 Age [y:d:h:m:s]: 00:283:09:37:54
Block: 1037996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202554 RingCT/type: yes/0
Extra: 012379ca47f370fca2bbb0d841c480221e04c7b13ff25e35eefdc4668e8aaeb27c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a538bbe90ebb2ce78918038a9eaecf8f0101d58a6908fd67262e1200abcf16 0.600000000000 1506555 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": 1038006, "vin": [ { "gen": { "height": 1037996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a538bbe90ebb2ce78918038a9eaecf8f0101d58a6908fd67262e1200abcf16" } } ], "extra": [ 1, 35, 121, 202, 71, 243, 112, 252, 162, 187, 176, 216, 65, 196, 128, 34, 30, 4, 199, 177, 63, 242, 94, 53, 238, 253, 196, 102, 142, 138, 174, 178, 124, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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