Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57d19b25d305b0621930365e126880b88d53c3e243029113710e9c996e51cfa2

Tx prefix hash: ba46ae1ec370e0e43c4081c5e21888205dc656eacc5f8d1dfa5445e364adc4e9
Tx public key: 6db6562ab21ec7c7ea440176f2a92c4e4aff7559c8cef2fedf8605e4f8ea37d7
Timestamp: 1732893435 Timestamp [UCT]: 2024-11-29 15:17:15 Age [y:d:h:m:s]: 00:121:09:33:15
Block: 1164351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86565 RingCT/type: yes/0
Extra: 016db6562ab21ec7c7ea440176f2a92c4e4aff7559c8cef2fedf8605e4f8ea37d7021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5959ef5a5c4cb155780bf26593e838f7e6c8252ed0570e04fd2966cdcc1bac68 0.600000000000 1650024 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": 1164361, "vin": [ { "gen": { "height": 1164351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5959ef5a5c4cb155780bf26593e838f7e6c8252ed0570e04fd2966cdcc1bac68" } } ], "extra": [ 1, 109, 182, 86, 42, 178, 30, 199, 199, 234, 68, 1, 118, 242, 169, 44, 78, 74, 255, 117, 89, 200, 206, 242, 254, 223, 134, 5, 228, 248, 234, 55, 215, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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