Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015b248e2db47548b8c596063d89a52bf0ac8e12a0e3a5b6069a0881143f5333

Tx prefix hash: 17e2bcb67b5b48d3d82453acce7c8e25a0b81bc4224e527c0d557d34ea87bcf6
Tx public key: 5728286b7fb0277a11189d8d83e8971a0beb46d4d2c6cc4f336da2f538abf0ed
Timestamp: 1735949374 Timestamp [UCT]: 2025-01-04 00:09:34 Age [y:d:h:m:s]: 00:353:16:05:39
Block: 1189658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250306 RingCT/type: yes/0
Extra: 015728286b7fb0277a11189d8d83e8971a0beb46d4d2c6cc4f336da2f538abf0ed02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8e1bd748ba7b47e2c03d76e8cdc0204278f7295a1a20f0c0c95c29661030d8d 0.600000000000 1676169 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": 1189668, "vin": [ { "gen": { "height": 1189658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8e1bd748ba7b47e2c03d76e8cdc0204278f7295a1a20f0c0c95c29661030d8d" } } ], "extra": [ 1, 87, 40, 40, 107, 127, 176, 39, 122, 17, 24, 157, 141, 131, 232, 151, 26, 11, 235, 70, 212, 210, 198, 204, 79, 51, 109, 162, 245, 56, 171, 240, 237, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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