Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4a61e14e46b32d8146aebfaa103999be492034cd5aaf95a89d9fdab4164431

Tx prefix hash: 5d9a2893507ef44c27ddc61729b5d4b648bf4d7c11b922b9fe8942d00baecbb9
Tx public key: db8ec235a8e77f397514161a0ab85d2ae2bb1a169e2e5586f10d3c2e27525279
Timestamp: 1736495743 Timestamp [UCT]: 2025-01-10 07:55:43 Age [y:d:h:m:s]: 00:087:22:16:19
Block: 1194167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62621 RingCT/type: yes/0
Extra: 01db8ec235a8e77f397514161a0ab85d2ae2bb1a169e2e5586f10d3c2e27525279021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2a28eaad899440d0421da8e4e60db732d9aec0088caed7f8d34fc404c0a3a18 0.600000000000 1680734 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": 1194177, "vin": [ { "gen": { "height": 1194167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a28eaad899440d0421da8e4e60db732d9aec0088caed7f8d34fc404c0a3a18" } } ], "extra": [ 1, 219, 142, 194, 53, 168, 231, 127, 57, 117, 20, 22, 26, 10, 184, 93, 42, 226, 187, 26, 22, 158, 46, 85, 134, 241, 13, 60, 46, 39, 82, 82, 121, 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