Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8cb91dbc230db279f8ba22a3e87e6d913cc214800ed4b100a8271d3d19b037

Tx prefix hash: f880263600a40cb956725638f6c95357a6e06a1429253c7097c2b049244f5ad4
Tx public key: 369f7c102d1b3e29f51b703bbd3229a1df83e3c53f8fe817b42d07105d1af59f
Timestamp: 1709510010 Timestamp [UCT]: 2024-03-03 23:53:30 Age [y:d:h:m:s]: 01:031:21:51:17
Block: 970595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283797 RingCT/type: yes/0
Extra: 01369f7c102d1b3e29f51b703bbd3229a1df83e3c53f8fe817b42d07105d1af59f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dca74154fcef6a9f6a67b79e63eec193d4c449dd8b460aa6f9fb15e2fd7d619 0.600000000000 1430454 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": 970605, "vin": [ { "gen": { "height": 970595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dca74154fcef6a9f6a67b79e63eec193d4c449dd8b460aa6f9fb15e2fd7d619" } } ], "extra": [ 1, 54, 159, 124, 16, 45, 27, 62, 41, 245, 27, 112, 59, 189, 50, 41, 161, 223, 131, 227, 197, 63, 143, 232, 23, 180, 45, 7, 16, 93, 26, 245, 159, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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