Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d85f91188e4b565205d73213d8bb0e19699a84e581707350c52a34fa009053

Tx prefix hash: b970d898d4821ba9ada04ed6c2ca8e9ea799f1a0cb2445b8dbd5ed4686cbdc4c
Tx public key: 40900aee17f0f4c5fcc699a86c02290545357f7f4376fb2fc950586f62c0772f
Timestamp: 1736832757 Timestamp [UCT]: 2025-01-14 05:32:37 Age [y:d:h:m:s]: 00:155:10:12:43
Block: 1196970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110784 RingCT/type: yes/0
Extra: 0140900aee17f0f4c5fcc699a86c02290545357f7f4376fb2fc950586f62c0772f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b7271b39aa2c73967562c2b4185eab2d3a432c91ab59e6e90ae94d847795d3e 0.600000000000 1683575 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": 1196980, "vin": [ { "gen": { "height": 1196970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b7271b39aa2c73967562c2b4185eab2d3a432c91ab59e6e90ae94d847795d3e" } } ], "extra": [ 1, 64, 144, 10, 238, 23, 240, 244, 197, 252, 198, 153, 168, 108, 2, 41, 5, 69, 53, 127, 127, 67, 118, 251, 47, 201, 80, 88, 111, 98, 192, 119, 47, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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