Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91481fdd76e36ef4daf0359074314655fc16627997be8081e74a79b98b7ba101

Tx prefix hash: 3ae3b5ffeeb0a7eeccc550b211df790d54a7cbd1968968fe23c89b945cff0e02
Tx public key: e3a3cc14059b3fbe388c5e6db37dbe1518bd6caff0f9b3dc2ba457a4edb4ee9a
Timestamp: 1736553897 Timestamp [UCT]: 2025-01-11 00:04:57 Age [y:d:h:m:s]: 00:076:08:45:56
Block: 1194649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54359 RingCT/type: yes/0
Extra: 01e3a3cc14059b3fbe388c5e6db37dbe1518bd6caff0f9b3dc2ba457a4edb4ee9a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9ad8d6a9f48c25980fe8992f95366417d8951db1a1cf488955be342eece2e03 0.600000000000 1681226 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": 1194659, "vin": [ { "gen": { "height": 1194649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ad8d6a9f48c25980fe8992f95366417d8951db1a1cf488955be342eece2e03" } } ], "extra": [ 1, 227, 163, 204, 20, 5, 155, 63, 190, 56, 140, 94, 109, 179, 125, 190, 21, 24, 189, 108, 175, 240, 249, 179, 220, 43, 164, 87, 164, 237, 180, 238, 154, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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