Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43be22b130d0ea48fa62663f5dc2b69b1cc76d3bc03783b16be27ee8c4ef8b72

Tx prefix hash: 1a8957b15ea30142f905988a8fec12156f952b5e69c42dd426f94e5b5cac456e
Tx public key: cf9c51e6515d21a9e3510b017cea448447a0e4186dbfc98eaf2504e1f8ee24f1
Timestamp: 1736305842 Timestamp [UCT]: 2025-01-08 03:10:42 Age [y:d:h:m:s]: 00:304:13:10:30
Block: 1192600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215164 RingCT/type: yes/0
Extra: 01cf9c51e6515d21a9e3510b017cea448447a0e4186dbfc98eaf2504e1f8ee24f10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a3a25b9a28cc4016c48ff8824646fc9bf08a0fb43a62bea61cc86eb0608132e 0.600000000000 1679155 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": 1192610, "vin": [ { "gen": { "height": 1192600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a3a25b9a28cc4016c48ff8824646fc9bf08a0fb43a62bea61cc86eb0608132e" } } ], "extra": [ 1, 207, 156, 81, 230, 81, 93, 33, 169, 227, 81, 11, 1, 124, 234, 68, 132, 71, 160, 228, 24, 109, 191, 201, 142, 175, 37, 4, 225, 248, 238, 36, 241, 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