Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be80461ca676147719b1223c337edcc9b233c003cbd4f9f7bf5cd890b868912

Tx prefix hash: 5de80650998c01cc99e5a98ac5dd978c70f851e38eaa8fe15c8d46a85e3e4fff
Tx public key: bcd686b06c413b1736717ce4e09ef92335dcb244041fe5e83d83a9f4b1796ad2
Timestamp: 1696275715 Timestamp [UCT]: 2023-10-02 19:41:55 Age [y:d:h:m:s]: 01:184:09:02:33
Block: 861073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392814 RingCT/type: yes/0
Extra: 01bcd686b06c413b1736717ce4e09ef92335dcb244041fe5e83d83a9f4b1796ad2021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.860810871000 dcy

stealth address amount amount idx
00: 6012b259b1dfe71bd855713bc8d9fa02b1ba467ed68d465597711cfc0b298352 0.860810871000 1315385 of 0

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": 861083, "vin": [ { "gen": { "height": 861073 } } ], "vout": [ { "amount": 860810871, "target": { "key": "6012b259b1dfe71bd855713bc8d9fa02b1ba467ed68d465597711cfc0b298352" } } ], "extra": [ 1, 188, 214, 134, 176, 108, 65, 59, 23, 54, 113, 124, 228, 224, 158, 249, 35, 53, 220, 178, 68, 4, 31, 229, 232, 61, 131, 169, 244, 177, 121, 106, 210, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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