Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8265c6b0fbbf406d7d7ff52d49bc04b7665d044d282d8a2073c0b255a454fc68

Tx prefix hash: 8d8f8050d8563389e3571345c57b077f1915b48eb3e4ed4e46405aa88dddcac5
Tx public key: b11789cd905173494a225e0adb390bb329c12c9057dcfef051b7fdd05d3c42c6
Timestamp: 1702828685 Timestamp [UCT]: 2023-12-17 15:58:05 Age [y:d:h:m:s]: 00:346:22:53:54
Block: 915195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248435 RingCT/type: yes/0
Extra: 01b11789cd905173494a225e0adb390bb329c12c9057dcfef051b7fdd05d3c42c6021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 085cdaa9c1804b88d1c185b0609f5b5a518ea07a943293fedde0b7a75a911034 0.600000000000 1372583 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": 915205, "vin": [ { "gen": { "height": 915195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "085cdaa9c1804b88d1c185b0609f5b5a518ea07a943293fedde0b7a75a911034" } } ], "extra": [ 1, 177, 23, 137, 205, 144, 81, 115, 73, 74, 34, 94, 10, 219, 57, 11, 179, 41, 193, 44, 144, 87, 220, 254, 240, 81, 183, 253, 208, 93, 60, 66, 198, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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