Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b24b85aeeb365b4fb5c2883fae15b4973f88c7de67a9673618cefb9fb065e1

Tx prefix hash: 3e032090a3a03a4766481a1609217d508b07c2c723e4e70bd443fe69277c69f0
Tx public key: a21f0164a2450fad7cc2e6343fcad5f8a643055a33405988e1bc445c55484d47
Timestamp: 1736320272 Timestamp [UCT]: 2025-01-08 07:11:12 Age [y:d:h:m:s]: 00:082:13:09:44
Block: 1192720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58776 RingCT/type: yes/0
Extra: 01a21f0164a2450fad7cc2e6343fcad5f8a643055a33405988e1bc445c55484d470211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce9fedcdcd04ee634c6424d4b0b86b1e9fbedd38ead132e3f8c3d0e8754962b7 0.600000000000 1679275 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": 1192730, "vin": [ { "gen": { "height": 1192720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce9fedcdcd04ee634c6424d4b0b86b1e9fbedd38ead132e3f8c3d0e8754962b7" } } ], "extra": [ 1, 162, 31, 1, 100, 162, 69, 15, 173, 124, 194, 230, 52, 63, 202, 213, 248, 166, 67, 5, 90, 51, 64, 89, 136, 225, 188, 68, 92, 85, 72, 77, 71, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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