Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b1adaec3f0beca9ae5c08622e65286f038a3f080f5193a5a9b57d6f3096868b

Tx prefix hash: 8f51c4fb1e4ca265a3ee258f6058fee17379555f6cba29b56b767baeb6ca98e0
Tx public key: dd1f45b95ba1f2c6aba8869bd70ca87c3a88596db9cc63b57e25e093b269f731
Timestamp: 1725797135 Timestamp [UCT]: 2024-09-08 12:05:35 Age [y:d:h:m:s]: 00:077:12:23:52
Block: 1105621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55425 RingCT/type: yes/0
Extra: 01dd1f45b95ba1f2c6aba8869bd70ca87c3a88596db9cc63b57e25e093b269f73102110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba80fa5cbdcd8cc51244c8a5d181768895f30aee5c121648e44bcdfe7fa40739 0.600000000000 1583012 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": 1105631, "vin": [ { "gen": { "height": 1105621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba80fa5cbdcd8cc51244c8a5d181768895f30aee5c121648e44bcdfe7fa40739" } } ], "extra": [ 1, 221, 31, 69, 185, 91, 161, 242, 198, 171, 168, 134, 155, 215, 12, 168, 124, 58, 136, 89, 109, 185, 204, 99, 181, 126, 37, 224, 147, 178, 105, 247, 49, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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