Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107f2cca972216c7e585bbe8f7c27f5e7917d1e0955e809e88641e8954c16851

Tx prefix hash: b63b27741828fa6737757dc07aa6ecd0c396870ed3bf06a7695dc561586fd0d7
Tx public key: 25571eaaef66a4e9fffda980fd6a38baa8baa8e9b7e70e7f25dd4ebdca31c1c2
Timestamp: 1703601344 Timestamp [UCT]: 2023-12-26 14:35:44 Age [y:d:h:m:s]: 01:321:20:35:02
Block: 921602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488871 RingCT/type: yes/0
Extra: 0125571eaaef66a4e9fffda980fd6a38baa8baa8e9b7e70e7f25dd4ebdca31c1c20211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538d20d0f1b525b9cf9de06ab19374450e990e165cf8271ddb129167efd79827 0.600000000000 1379292 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": 921612, "vin": [ { "gen": { "height": 921602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538d20d0f1b525b9cf9de06ab19374450e990e165cf8271ddb129167efd79827" } } ], "extra": [ 1, 37, 87, 30, 170, 239, 102, 164, 233, 255, 253, 169, 128, 253, 106, 56, 186, 168, 186, 168, 233, 183, 231, 14, 127, 37, 221, 78, 189, 202, 49, 193, 194, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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