Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c288244541e1b095ad2da9558de022fc035dbff97408bc9a27a85707702ae07

Tx prefix hash: f463c68b78d5d82104b73dcc7175a94a0c8680d1f71d9ecefb49a67d809ee20a
Tx public key: 508ab2f8729fe60fe4d171ed9f8b908ea66bc2ad9c86d8f4f1c779c98f0815ca
Timestamp: 1718054857 Timestamp [UCT]: 2024-06-10 21:27:37 Age [y:d:h:m:s]: 00:311:12:43:35
Block: 1041429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222645 RingCT/type: yes/0
Extra: 01508ab2f8729fe60fe4d171ed9f8b908ea66bc2ad9c86d8f4f1c779c98f0815ca0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974cd5eb3e1ef02aedb1c2a219a27be797529482b13b4d4336a5a1091715f636 0.600000000000 1510102 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": 1041439, "vin": [ { "gen": { "height": 1041429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974cd5eb3e1ef02aedb1c2a219a27be797529482b13b4d4336a5a1091715f636" } } ], "extra": [ 1, 80, 138, 178, 248, 114, 159, 230, 15, 228, 209, 113, 237, 159, 139, 144, 142, 166, 107, 194, 173, 156, 134, 216, 244, 241, 199, 121, 201, 143, 8, 21, 202, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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