Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713ee741b929f7361fb698753db792f338c12ed5ef1a35d3bc1dc5b75d726e56

Tx prefix hash: 203829a764f284493ced6923bcf0a67521b5c4c9b77aa014632325efb22b45e6
Tx public key: 87756fb2b1b9d9ae558e165a43080e5f0d871016262016ad81da0f8a4809a4ac
Timestamp: 1712287984 Timestamp [UCT]: 2024-04-05 03:33:04 Age [y:d:h:m:s]: 01:002:11:09:25
Block: 993586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262748 RingCT/type: yes/0
Extra: 0187756fb2b1b9d9ae558e165a43080e5f0d871016262016ad81da0f8a4809a4ac02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 276d0a71c6e90d37ced532237ac6c195cd6d390ba43f0c21a76efa99633277e2 0.600000000000 1453972 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": 993596, "vin": [ { "gen": { "height": 993586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "276d0a71c6e90d37ced532237ac6c195cd6d390ba43f0c21a76efa99633277e2" } } ], "extra": [ 1, 135, 117, 111, 178, 177, 185, 217, 174, 85, 142, 22, 90, 67, 8, 14, 95, 13, 135, 16, 22, 38, 32, 22, 173, 129, 218, 15, 138, 72, 9, 164, 172, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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