Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632245e46c8fcb961a8a20361d0509a7170e2b8f114655b8b2dbdea8bb56ed76

Tx prefix hash: c2cb688c9b75ffe1613f0a8424cbb49ba7a5221503255cb5bd6a2a5e2be84893
Tx public key: a0fc99682d341061b03e60abdff894d3ad6c7c965fbd429df4cd3379e682e18f
Timestamp: 1711894420 Timestamp [UCT]: 2024-03-31 14:13:40 Age [y:d:h:m:s]: 01:245:07:34:23
Block: 990374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434021 RingCT/type: yes/0
Extra: 01a0fc99682d341061b03e60abdff894d3ad6c7c965fbd429df4cd3379e682e18f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ba0f4bdbed3fff19a56fed973f0aefd66dcb6e5381c6089714e6722d87a4fc9 0.600000000000 1450696 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": 990384, "vin": [ { "gen": { "height": 990374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ba0f4bdbed3fff19a56fed973f0aefd66dcb6e5381c6089714e6722d87a4fc9" } } ], "extra": [ 1, 160, 252, 153, 104, 45, 52, 16, 97, 176, 62, 96, 171, 223, 248, 148, 211, 173, 108, 124, 150, 95, 189, 66, 157, 244, 205, 51, 121, 230, 130, 225, 143, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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