Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec474009ef7a4522aa83fac7f92bb017f0dd5f16e3b866af0823841fd13f04a

Tx prefix hash: af264408b293e6868ca38e7e5819059f435d43250f27a0a9871c3a0a39ef2063
Tx public key: b21835b7c4e2f9048bc9125ffd395017a24b7fde33d19d6f3480f8559f39c314
Timestamp: 1726133497 Timestamp [UCT]: 2024-09-12 09:31:37 Age [y:d:h:m:s]: 00:163:13:00:07
Block: 1108396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116684 RingCT/type: yes/0
Extra: 01b21835b7c4e2f9048bc9125ffd395017a24b7fde33d19d6f3480f8559f39c31402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385c6d11eda9eacc5a6d6f5961570fccbe57f8f9bf1eab808983cdc8c459c9bf 0.600000000000 1586279 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": 1108406, "vin": [ { "gen": { "height": 1108396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385c6d11eda9eacc5a6d6f5961570fccbe57f8f9bf1eab808983cdc8c459c9bf" } } ], "extra": [ 1, 178, 24, 53, 183, 196, 226, 249, 4, 139, 201, 18, 95, 253, 57, 80, 23, 162, 75, 127, 222, 51, 209, 157, 111, 52, 128, 248, 85, 159, 57, 195, 20, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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