Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df25ed52ef08e77d1e6adcd30c56f7d72a859a82ec6d3cbcf57cb5d7daf72a9e

Tx prefix hash: 2e486c3dbd2f95e1e02b610ae599b3916a0a4872734d5706d7f720fcad0c0434
Tx public key: f1f825078a6b61977a876c972a354cca6918664cd1650a2a8b53157519d0f0dc
Timestamp: 1673818421 Timestamp [UCT]: 2023-01-15 21:33:41 Age [y:d:h:m:s]: 02:062:07:53:50
Block: 675549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566217 RingCT/type: yes/0
Extra: 01f1f825078a6b61977a876c972a354cca6918664cd1650a2a8b53157519d0f0dc0211000000068b7b6602000000000000000000

1 output(s) for total of 3.545077047000 dcy

stealth address amount amount idx
00: ba810932e49c0feb6cf18ef767c2d96d0affe7a3b4a9cc13fd30c4262f69a6b7 3.545077047000 1117228 of 0

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": 675559, "vin": [ { "gen": { "height": 675549 } } ], "vout": [ { "amount": 3545077047, "target": { "key": "ba810932e49c0feb6cf18ef767c2d96d0affe7a3b4a9cc13fd30c4262f69a6b7" } } ], "extra": [ 1, 241, 248, 37, 7, 138, 107, 97, 151, 122, 135, 108, 151, 42, 53, 76, 202, 105, 24, 102, 76, 209, 101, 10, 42, 139, 83, 21, 117, 25, 208, 240, 220, 2, 17, 0, 0, 0, 6, 139, 123, 102, 2, 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