Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46c8fb1e94ea1b55a23b2a81e3e2f8339ef823bc7f890ad8af9003f0ee85de3a

Tx prefix hash: 3faec7186ace425fa0f236d2aa531f12ac95481aa8c0553c1de12c382e7b3791
Tx public key: be4c2c04bedb284cff2df2f85581809b768aaa351f34d62aad5ff52e0864dd45
Timestamp: 1735469195 Timestamp [UCT]: 2024-12-29 10:46:35 Age [y:d:h:m:s]: 00:126:04:34:33
Block: 1185665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89999 RingCT/type: yes/0
Extra: 01be4c2c04bedb284cff2df2f85581809b768aaa351f34d62aad5ff52e0864dd450211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63427fd7fd356d2cb019ef7df1c73cc8754a2860dd517d865de07bade33e1afa 0.600000000000 1672140 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": 1185675, "vin": [ { "gen": { "height": 1185665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63427fd7fd356d2cb019ef7df1c73cc8754a2860dd517d865de07bade33e1afa" } } ], "extra": [ 1, 190, 76, 44, 4, 190, 219, 40, 76, 255, 45, 242, 248, 85, 129, 128, 155, 118, 138, 170, 53, 31, 52, 214, 42, 173, 95, 245, 46, 8, 100, 221, 69, 2, 17, 0, 0, 0, 3, 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