Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160cfff3487fcca60ed47897ba07537222d0423c3ded67ab9864360753f19bff

Tx prefix hash: 17c3fc6b53cfa1f9870275f25c4fe139e1b5640a1c9f150108570cb7b4001b86
Tx public key: daa1103ea9ecb1a1b6c72c5c0d2648bd6a00227790c52a8873b7e9dfb8ba8d11
Timestamp: 1725200579 Timestamp [UCT]: 2024-09-01 14:22:59 Age [y:d:h:m:s]: 01:068:05:54:50
Block: 1100675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307200 RingCT/type: yes/0
Extra: 01daa1103ea9ecb1a1b6c72c5c0d2648bd6a00227790c52a8873b7e9dfb8ba8d1102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daa8677b9ce93b1d29564727257a1426e0c99e98fc37beca448e5594e44074b1 0.600000000000 1576654 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": 1100685, "vin": [ { "gen": { "height": 1100675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daa8677b9ce93b1d29564727257a1426e0c99e98fc37beca448e5594e44074b1" } } ], "extra": [ 1, 218, 161, 16, 62, 169, 236, 177, 161, 182, 199, 44, 92, 13, 38, 72, 189, 106, 0, 34, 119, 144, 197, 42, 136, 115, 183, 233, 223, 184, 186, 141, 17, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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