Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899f1ebe38b2829eb4ccf6b90493d60b900a6e19f4e5f89eabfd649472e50914

Tx prefix hash: 228de44d54ffeae53c55836fb4b753e43b95f6f4b11f84e812522c2fe806aca4
Tx public key: e96e0b0f41aaedc1d73a313e44e4c3e81b7dcd3ebbfdef71a143ea2d5bede01d
Timestamp: 1761730622 Timestamp [UCT]: 2025-10-29 09:37:02 Age [y:d:h:m:s]: 00:010:23:56:26
Block: 1400408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7866 RingCT/type: yes/0
Extra: 01e96e0b0f41aaedc1d73a313e44e4c3e81b7dcd3ebbfdef71a143ea2d5bede01d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff3725cc5c92673ca0160f98c498bec7ad98f544414b79a0ff2aeb81d048b9b8 0.600000000000 1888715 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": 1400418, "vin": [ { "gen": { "height": 1400408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff3725cc5c92673ca0160f98c498bec7ad98f544414b79a0ff2aeb81d048b9b8" } } ], "extra": [ 1, 233, 110, 11, 15, 65, 170, 237, 193, 215, 58, 49, 62, 68, 228, 195, 232, 27, 125, 205, 62, 187, 253, 239, 113, 161, 67, 234, 45, 91, 237, 224, 29, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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