Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13c72557ea21e72b5d1e43f72b33913e48bafa3b7fde27999244155de84619a1

Tx prefix hash: 79f6932f7efcc3c5b3c546786f5a679d9e6a417e650c4ba281ebc55f9ed9af72
Tx public key: 3275f3572e8a4c4d9c4f8d0ea1c8fcc72c9b097b76bda648ad3c90ae72105b29
Timestamp: 1727909930 Timestamp [UCT]: 2024-10-02 22:58:50 Age [y:d:h:m:s]: 00:189:07:51:24
Block: 1123136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135114 RingCT/type: yes/0
Extra: 013275f3572e8a4c4d9c4f8d0ea1c8fcc72c9b097b76bda648ad3c90ae72105b29021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f8b1c5ba14a677dfbd3749c2c6a333004f707bf4addfa0a85da536d851630cf 0.600000000000 1605669 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": 1123146, "vin": [ { "gen": { "height": 1123136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f8b1c5ba14a677dfbd3749c2c6a333004f707bf4addfa0a85da536d851630cf" } } ], "extra": [ 1, 50, 117, 243, 87, 46, 138, 76, 77, 156, 79, 141, 14, 161, 200, 252, 199, 44, 155, 9, 123, 118, 189, 166, 72, 173, 60, 144, 174, 114, 16, 91, 41, 2, 17, 0, 0, 0, 2, 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