Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d7882f63dafd460b699c2062e42fa6385678b2ee6520001277337e11ea2c0cf

Tx prefix hash: bbebc5e9c8553a3f9e6af7f512c289c02704751360e241c778399892dee280d1
Tx public key: 9a4586c483c207d60b5dbfa8fcd1a1409af2c9a6f58226d92737c2a668962eef
Timestamp: 1703086057 Timestamp [UCT]: 2023-12-20 15:27:37 Age [y:d:h:m:s]: 01:155:02:12:03
Block: 917335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372001 RingCT/type: yes/0
Extra: 019a4586c483c207d60b5dbfa8fcd1a1409af2c9a6f58226d92737c2a668962eef0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5172feda0323d95b86322b8d461a1d8c55ffaa604d5ca380e445fce2a28a6083 0.600000000000 1374907 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": 917345, "vin": [ { "gen": { "height": 917335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5172feda0323d95b86322b8d461a1d8c55ffaa604d5ca380e445fce2a28a6083" } } ], "extra": [ 1, 154, 69, 134, 196, 131, 194, 7, 214, 11, 93, 191, 168, 252, 209, 161, 64, 154, 242, 201, 166, 245, 130, 38, 217, 39, 55, 194, 166, 104, 150, 46, 239, 2, 17, 0, 0, 0, 5, 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