Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce2706816396339120b01702816c61e2e951f1b78ca332d6dc1dbb56f124c3a

Tx prefix hash: 5f4b685db5140fda0ad94f37b1cad990e5cb7f1acda74acc03a5683a328dff5d
Tx public key: c94d5fad652d4e8d7c1888b3b753a73d82202f02f17b67ffc35259e477de0488
Timestamp: 1704970130 Timestamp [UCT]: 2024-01-11 10:48:50 Age [y:d:h:m:s]: 01:069:10:58:48
Block: 932936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310753 RingCT/type: yes/0
Extra: 01c94d5fad652d4e8d7c1888b3b753a73d82202f02f17b67ffc35259e477de048802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7ae287ab1279261043916e2d02488b63ff655d2251aed9cb8f483a72296c6ab 0.600000000000 1390876 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": 932946, "vin": [ { "gen": { "height": 932936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7ae287ab1279261043916e2d02488b63ff655d2251aed9cb8f483a72296c6ab" } } ], "extra": [ 1, 201, 77, 95, 173, 101, 45, 78, 141, 124, 24, 136, 179, 183, 83, 167, 61, 130, 32, 47, 2, 241, 123, 103, 255, 195, 82, 89, 228, 119, 222, 4, 136, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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