Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd77f5d4d8409924916fe0ee4b707e359bc74fe88c1a725e5e45cb7b5571adc

Tx prefix hash: 8fdfa2d9320e8c59480589a4726606c71b0632fa966b3fc3f1e79ff4b28a8123
Tx public key: 2ef6e781825b31cbf5de0f84829d14292d09f8dc91dbc41e5e6c04edf9a9e849
Timestamp: 1672679435 Timestamp [UCT]: 2023-01-02 17:10:35 Age [y:d:h:m:s]: 01:311:14:12:50
Block: 666117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483685 RingCT/type: yes/0
Extra: 012ef6e781825b31cbf5de0f84829d14292d09f8dc91dbc41e5e6c04edf9a9e849021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.809586364000 dcy

stealth address amount amount idx
00: b878b9b61e49febbb4b76dc2b3adea8096b4d35ae11cd3eaf37bf0326d3abc38 3.809586364000 1107212 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": 666127, "vin": [ { "gen": { "height": 666117 } } ], "vout": [ { "amount": 3809586364, "target": { "key": "b878b9b61e49febbb4b76dc2b3adea8096b4d35ae11cd3eaf37bf0326d3abc38" } } ], "extra": [ 1, 46, 246, 231, 129, 130, 91, 49, 203, 245, 222, 15, 132, 130, 157, 20, 41, 45, 9, 248, 220, 145, 219, 196, 30, 94, 108, 4, 237, 249, 169, 232, 73, 2, 17, 0, 0, 0, 2, 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