Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f87f08366f71a32016a8568eaa81ca4cebff0327dfbbb5be414e673e15542a

Tx prefix hash: 0c9fc0b879995b847242ac83a932bc5809204f26bbd6fea4b089fa8e6f3f1ab0
Tx public key: f27b84e7e44ddc498f9aabd40f2a753e1e31b529de9f2461ae7424de79df7390
Timestamp: 1726048353 Timestamp [UCT]: 2024-09-11 09:52:33 Age [y:d:h:m:s]: 00:119:19:47:31
Block: 1107705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85693 RingCT/type: yes/0
Extra: 01f27b84e7e44ddc498f9aabd40f2a753e1e31b529de9f2461ae7424de79df7390021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20b9ea67fce98919b3715bb97bc8dceed74d78d7c884358f9197542e871a997e 0.600000000000 1585334 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": 1107715, "vin": [ { "gen": { "height": 1107705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20b9ea67fce98919b3715bb97bc8dceed74d78d7c884358f9197542e871a997e" } } ], "extra": [ 1, 242, 123, 132, 231, 228, 77, 220, 73, 143, 154, 171, 212, 15, 42, 117, 62, 30, 49, 181, 41, 222, 159, 36, 97, 174, 116, 36, 222, 121, 223, 115, 144, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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