Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ca6e4b6193eeb97c20a1be9264225c17183eb8d71abaea321d98fc3d0c00c1

Tx prefix hash: ddc841116396ae94a092a58205f94560960b93cb42bf1a2ed0f1766600e94e8b
Tx public key: c4a02a96cc79c87bdcc377a8b0fddba8635f3a6977f56321181c9f2dfac6db20
Timestamp: 1731067816 Timestamp [UCT]: 2024-11-08 12:10:16 Age [y:d:h:m:s]: 00:156:13:29:23
Block: 1149231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111745 RingCT/type: yes/0
Extra: 01c4a02a96cc79c87bdcc377a8b0fddba8635f3a6977f56321181c9f2dfac6db200211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb15fa89a7d46271e53e72f917f75f0d1c18f790030d8f8e0ba1662026a0ef76 0.600000000000 1634266 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": 1149241, "vin": [ { "gen": { "height": 1149231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb15fa89a7d46271e53e72f917f75f0d1c18f790030d8f8e0ba1662026a0ef76" } } ], "extra": [ 1, 196, 160, 42, 150, 204, 121, 200, 123, 220, 195, 119, 168, 176, 253, 219, 168, 99, 95, 58, 105, 119, 245, 99, 33, 24, 28, 159, 45, 250, 198, 219, 32, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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