Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0695c0716fdc45580fd489b6f61a415eabf80b5e1d91a01e18b435636c99fb

Tx prefix hash: 2347627161776ddc482803c9dbe1a6b2f7b5444c76112dba1dffb16338b75fbd
Tx public key: 3a6da2a6da29ef2a8e53ce9692037a96f83b83e93c3d66aa69cf30823896c945
Timestamp: 1730069415 Timestamp [UCT]: 2024-10-27 22:50:15 Age [y:d:h:m:s]: 00:157:14:12:08
Block: 1140984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112437 RingCT/type: yes/0
Extra: 013a6da2a6da29ef2a8e53ce9692037a96f83b83e93c3d66aa69cf30823896c94502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 934bc9bfe89015d1995a8f966ba829aa8e8e9f85be9cf8edabf963248f66c309 0.600000000000 1624791 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": 1140994, "vin": [ { "gen": { "height": 1140984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "934bc9bfe89015d1995a8f966ba829aa8e8e9f85be9cf8edabf963248f66c309" } } ], "extra": [ 1, 58, 109, 162, 166, 218, 41, 239, 42, 142, 83, 206, 150, 146, 3, 122, 150, 248, 59, 131, 233, 60, 61, 102, 170, 105, 207, 48, 130, 56, 150, 201, 69, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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