Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b79f24b115c5498d3b4bee46f470cd9af87c5f27cc3c3763a84dd550ff4bc01

Tx prefix hash: 5655697a4c6387f834fe656f0c82a91796799a80748d6d5ca467dd33ff94a049
Tx public key: bdd61a7ee6e50f427b63a79ac4eac9a0b7e41c24a356e2fb3e82fd1753b80448
Timestamp: 1733237044 Timestamp [UCT]: 2024-12-03 14:44:04 Age [y:d:h:m:s]: 00:121:20:46:52
Block: 1167195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86899 RingCT/type: yes/0
Extra: 01bdd61a7ee6e50f427b63a79ac4eac9a0b7e41c24a356e2fb3e82fd1753b80448021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87037b3d717532a9087b815e222e4da4468fdc6f188a8c4766185beaca7073bb 0.600000000000 1652890 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": 1167205, "vin": [ { "gen": { "height": 1167195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87037b3d717532a9087b815e222e4da4468fdc6f188a8c4766185beaca7073bb" } } ], "extra": [ 1, 189, 214, 26, 126, 230, 229, 15, 66, 123, 99, 167, 154, 196, 234, 201, 160, 183, 228, 28, 36, 163, 86, 226, 251, 62, 130, 253, 23, 83, 184, 4, 72, 2, 17, 0, 0, 0, 2, 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