Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c346d15c4a2014eb5ff39657af1e90b5a7ac20fe11c995225d4bee2939317a

Tx prefix hash: d94d39595cde8a088b6ff4df73834e1521aaeeb76f66a6cab8078fa8e8156820
Tx public key: 5522d2a71828b5e0488f31ebd975678b588f7fd3c13b4cc59c265a6ddb03b073
Timestamp: 1736690216 Timestamp [UCT]: 2025-01-12 13:56:56 Age [y:d:h:m:s]: 00:077:00:24:33
Block: 1195783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54812 RingCT/type: yes/0
Extra: 015522d2a71828b5e0488f31ebd975678b588f7fd3c13b4cc59c265a6ddb03b0730211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce427336e0d6c17807bc94a4d4c58e375e2c92e410f68ee3606fa2b673fa4449 0.600000000000 1682376 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": 1195793, "vin": [ { "gen": { "height": 1195783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce427336e0d6c17807bc94a4d4c58e375e2c92e410f68ee3606fa2b673fa4449" } } ], "extra": [ 1, 85, 34, 210, 167, 24, 40, 181, 224, 72, 143, 49, 235, 217, 117, 103, 139, 88, 143, 127, 211, 193, 59, 76, 197, 156, 38, 90, 109, 219, 3, 176, 115, 2, 17, 0, 0, 0, 3, 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