Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547e4f4b4bf97a7f422c5d084ba1f7026f8f16bc4f4e7c1e619d7836f4bbbefa

Tx prefix hash: 4434480d1a45701714a4171e4acf6167dd7b6d38bf341588491b03656ccf99f8
Tx public key: dd1ce150cca623d3b2e5bbd45ba2bd92a7fa2ed75776a48d99218038846c4e36
Timestamp: 1721498728 Timestamp [UCT]: 2024-07-20 18:05:28 Age [y:d:h:m:s]: 00:247:09:44:23
Block: 1069983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176725 RingCT/type: yes/0
Extra: 01dd1ce150cca623d3b2e5bbd45ba2bd92a7fa2ed75776a48d99218038846c4e36021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55df4c829227ae1ffc378bb8213ecee5bdea00e449cb1765fe09b8ce16a0121d 0.600000000000 1541628 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": 1069993, "vin": [ { "gen": { "height": 1069983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55df4c829227ae1ffc378bb8213ecee5bdea00e449cb1765fe09b8ce16a0121d" } } ], "extra": [ 1, 221, 28, 225, 80, 204, 166, 35, 211, 178, 229, 187, 212, 91, 162, 189, 146, 167, 250, 46, 215, 87, 118, 164, 141, 153, 33, 128, 56, 132, 108, 78, 54, 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