Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e82de159cfbf6d48188c37ca0c78f5f4ee42147ef5507723a30bbf2de71e77

Tx prefix hash: 8a28f895a61edcf0ae31573c29902c80026fd99a55d691f8f840891c3c664204
Tx public key: 0faf41fbdef2e425adc32bf563ec2a0e60bd57cff64e1bc1306f0f5c70d463a5
Timestamp: 1706655412 Timestamp [UCT]: 2024-01-30 22:56:52 Age [y:d:h:m:s]: 01:119:03:38:32
Block: 946901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346280 RingCT/type: yes/0
Extra: 010faf41fbdef2e425adc32bf563ec2a0e60bd57cff64e1bc1306f0f5c70d463a502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0cac098249f556b0c838df0e3305c4f49c2055716848a607921194df33a394d 0.600000000000 1405245 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": 946911, "vin": [ { "gen": { "height": 946901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0cac098249f556b0c838df0e3305c4f49c2055716848a607921194df33a394d" } } ], "extra": [ 1, 15, 175, 65, 251, 222, 242, 228, 37, 173, 195, 43, 245, 99, 236, 42, 14, 96, 189, 87, 207, 246, 78, 27, 193, 48, 111, 15, 92, 112, 212, 99, 165, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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