Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce74c3a5374ce5dd6a768427481f410a9173bc3f33b2dae55f5cf6b73cb7c0ca

Tx prefix hash: 2c06d5ff83b0e8d749e6a2a28b0203ff94373e7ee7fc431e4492270ee72ff48b
Tx public key: e5bea8152f6c59333d6be45e5fdaa45e6a287f8aa1cdce52a58597b1471aae34
Timestamp: 1731938783 Timestamp [UCT]: 2024-11-18 14:06:23 Age [y:d:h:m:s]: 01:002:13:07:31
Block: 1156435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260227 RingCT/type: yes/0
Extra: 01e5bea8152f6c59333d6be45e5fdaa45e6a287f8aa1cdce52a58597b1471aae34021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c4c4c7ab3d2fb4b44f5cabb5958d69bcd5a5ed630aa3a130e2ab3fe1101135 0.600000000000 1642058 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": 1156445, "vin": [ { "gen": { "height": 1156435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c4c4c7ab3d2fb4b44f5cabb5958d69bcd5a5ed630aa3a130e2ab3fe1101135" } } ], "extra": [ 1, 229, 190, 168, 21, 47, 108, 89, 51, 61, 107, 228, 94, 95, 218, 164, 94, 106, 40, 127, 138, 161, 205, 206, 82, 165, 133, 151, 177, 71, 26, 174, 52, 2, 17, 0, 0, 0, 4, 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