Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbee0bc074b4e8bc10f0bb9752f4cbf9fc08cea54878aaca38f4ea8460c56acf

Tx prefix hash: 4a978bbe89f2ff4a6234bedb885423501cf2788df39ee9de197eaee51d073cdb
Tx public key: fe937dc7e5766ef0123998e7b6337255f945cb4e24e047bc4db1f8415cbd7eba
Timestamp: 1736924505 Timestamp [UCT]: 2025-01-15 07:01:45 Age [y:d:h:m:s]: 00:182:21:35:42
Block: 1197717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129466 RingCT/type: yes/0
Extra: 01fe937dc7e5766ef0123998e7b6337255f945cb4e24e047bc4db1f8415cbd7eba0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da120c7ea2bbcdae29ddacbd3cf1ed3beb47d8f584540a707145aac03a09e10d 0.600000000000 1684332 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": 1197727, "vin": [ { "gen": { "height": 1197717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da120c7ea2bbcdae29ddacbd3cf1ed3beb47d8f584540a707145aac03a09e10d" } } ], "extra": [ 1, 254, 147, 125, 199, 229, 118, 110, 240, 18, 57, 152, 231, 182, 51, 114, 85, 249, 69, 203, 78, 36, 224, 71, 188, 77, 177, 248, 65, 92, 189, 126, 186, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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