Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b1e7ac252fe9f2864cb8e706e8b67ee77ddef126931f9970e2cb3f288f8c468

Tx prefix hash: a5638942a7b9543a3bc006d99adceb711986ab9893f72b0b10e7aea5cf930a0c
Tx public key: 94666e33ffe269298e812049ce78a3dbc1c3e9e678b2a1bc480b7275d40b9853
Timestamp: 1697085639 Timestamp [UCT]: 2023-10-12 04:40:39 Age [y:d:h:m:s]: 01:249:16:48:18
Block: 867794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439413 RingCT/type: yes/0
Extra: 0194666e33ffe269298e812049ce78a3dbc1c3e9e678b2a1bc480b7275d40b9853021100000002faf35c9c000000000000000000

1 output(s) for total of 0.817783361000 dcy

stealth address amount amount idx
00: def5927234eb26a60251043004e14b7a4f2789905ef9046e15c1f814190a8483 0.817783361000 1322512 of 0

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": 867804, "vin": [ { "gen": { "height": 867794 } } ], "vout": [ { "amount": 817783361, "target": { "key": "def5927234eb26a60251043004e14b7a4f2789905ef9046e15c1f814190a8483" } } ], "extra": [ 1, 148, 102, 110, 51, 255, 226, 105, 41, 142, 129, 32, 73, 206, 120, 163, 219, 193, 195, 233, 230, 120, 178, 161, 188, 72, 11, 114, 117, 212, 11, 152, 83, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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