Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f81c6afea2bfd31be42d38540798090766781b94fa109a1847d88aadadd4398f

Tx prefix hash: b6262856ed1a0ebde137c90c5b92cdd721632f4c9aabd0d67c818956acba8ea0
Tx public key: 6cd61e1f40a837c894b9b9b04cddf4d85cbe1d68ebc509dba04de512dd3712bb
Timestamp: 1734016233 Timestamp [UCT]: 2024-12-12 15:10:33 Age [y:d:h:m:s]: 00:089:18:55:31
Block: 1173668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63953 RingCT/type: yes/0
Extra: 016cd61e1f40a837c894b9b9b04cddf4d85cbe1d68ebc509dba04de512dd3712bb021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f129c7e93171743e21ad9ce27de75b2cf0f1c4fd87d1b2d31b34e374cd83f5d9 0.600000000000 1659715 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": 1173678, "vin": [ { "gen": { "height": 1173668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f129c7e93171743e21ad9ce27de75b2cf0f1c4fd87d1b2d31b34e374cd83f5d9" } } ], "extra": [ 1, 108, 214, 30, 31, 64, 168, 55, 200, 148, 185, 185, 176, 76, 221, 244, 216, 92, 190, 29, 104, 235, 197, 9, 219, 160, 77, 229, 18, 221, 55, 18, 187, 2, 17, 0, 0, 0, 5, 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