Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d48c144e7e376356b6789139b343153e728d43229568864f215ba218bd004e9

Tx prefix hash: e2c714e09cdeaf5f4716f1f308d69f34198cb16fdd09592a62cfa0756311dc47
Tx public key: f008d3e30381159fb8ac6e03719a3adb3bf286fb7a7c638d6ec1d0708a41a2bb
Timestamp: 1721082906 Timestamp [UCT]: 2024-07-15 22:35:06 Age [y:d:h:m:s]: 00:131:14:59:20
Block: 1066544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94172 RingCT/type: yes/0
Extra: 01f008d3e30381159fb8ac6e03719a3adb3bf286fb7a7c638d6ec1d0708a41a2bb02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 471c3f6b46820c08ffa8ced83a3227f59049fb20f016558b8dcf6343e186ab23 0.600000000000 1537203 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": 1066554, "vin": [ { "gen": { "height": 1066544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "471c3f6b46820c08ffa8ced83a3227f59049fb20f016558b8dcf6343e186ab23" } } ], "extra": [ 1, 240, 8, 211, 227, 3, 129, 21, 159, 184, 172, 110, 3, 113, 154, 58, 219, 59, 242, 134, 251, 122, 124, 99, 141, 110, 193, 208, 112, 138, 65, 162, 187, 2, 17, 0, 0, 0, 11, 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