Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870e6e57bbb0bd22fb592a19d66ba55965cc7171462de9423b8db7d6c4a9ee1b

Tx prefix hash: 4468fc07f9ffa9c0b82d9ba55291e23a1497b39c6bd8cbabb7a9cf40f9120872
Tx public key: bcc3fbcbb858b83c05696807f0ac258af9cfa4ae9ea193608bdaf918b5e836f4
Timestamp: 1715334023 Timestamp [UCT]: 2024-05-10 09:40:23 Age [y:d:h:m:s]: 00:230:07:45:32
Block: 1018877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164850 RingCT/type: yes/0
Extra: 01bcc3fbcbb858b83c05696807f0ac258af9cfa4ae9ea193608bdaf918b5e836f402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ec41e350eb5f3885d0dc585c62288873f640d0ff6100a6d038f9e6993b75d37 0.600000000000 1482686 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": 1018887, "vin": [ { "gen": { "height": 1018877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec41e350eb5f3885d0dc585c62288873f640d0ff6100a6d038f9e6993b75d37" } } ], "extra": [ 1, 188, 195, 251, 203, 184, 88, 184, 60, 5, 105, 104, 7, 240, 172, 37, 138, 249, 207, 164, 174, 158, 161, 147, 96, 139, 218, 249, 24, 181, 232, 54, 244, 2, 17, 0, 0, 0, 4, 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