Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb93e10e9cb456fceca1ecb864a3b831531894bfc33cad5b138b3887a1e0165

Tx prefix hash: 138c708648302615853e264b85fba4a3f88611e54d0f59da789fdc3a90b3be22
Tx public key: d7e53287f2d2223bef1ff81f86bddc1de717f2e673715b3dc9045aa412c7fdb0
Timestamp: 1648551296 Timestamp [UCT]: 2022-03-29 10:54:56 Age [y:d:h:m:s]: 03:032:06:35:01
Block: 468860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803304 RingCT/type: yes/0
Extra: 01d7e53287f2d2223bef1ff81f86bddc1de717f2e673715b3dc9045aa412c7fdb00211000000034a0f5013000000000000000000

1 output(s) for total of 17.158228143000 dcy

stealth address amount amount idx
00: 3291ccc202cf6a20b7e2fa87b2ddcc83cb9c880abdbb1ea5a4eadc7e7305a5f7 17.158228143000 887666 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": 468870, "vin": [ { "gen": { "height": 468860 } } ], "vout": [ { "amount": 17158228143, "target": { "key": "3291ccc202cf6a20b7e2fa87b2ddcc83cb9c880abdbb1ea5a4eadc7e7305a5f7" } } ], "extra": [ 1, 215, 229, 50, 135, 242, 210, 34, 59, 239, 31, 248, 31, 134, 189, 220, 29, 231, 23, 242, 230, 115, 113, 91, 61, 201, 4, 90, 164, 18, 199, 253, 176, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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