Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 141476f263a865d5af3011608254a0988b2e324abaa5d7857b58859f45ffbc9c

Tx prefix hash: 11d37d960f3422fbdc0bbcc7d82587caa8d67b30f2e70adbdd2029413a45b3a2
Tx public key: 13b075d4b77ea54eff62f2ccd67f67edd3f80c69909fe9e1c22c13202ba3b38b
Timestamp: 1729593492 Timestamp [UCT]: 2024-10-22 10:38:12 Age [y:d:h:m:s]: 00:094:13:46:03
Block: 1137060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67579 RingCT/type: yes/0
Extra: 0113b075d4b77ea54eff62f2ccd67f67edd3f80c69909fe9e1c22c13202ba3b38b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b168d9e0f6e12451de5c60d8fa709db6f3bb4521d1c428f1cb33c9793deb61d 0.600000000000 1620479 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": 1137070, "vin": [ { "gen": { "height": 1137060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b168d9e0f6e12451de5c60d8fa709db6f3bb4521d1c428f1cb33c9793deb61d" } } ], "extra": [ 1, 19, 176, 117, 212, 183, 126, 165, 78, 255, 98, 242, 204, 214, 127, 103, 237, 211, 248, 12, 105, 144, 159, 233, 225, 194, 44, 19, 32, 43, 163, 179, 139, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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