Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e430bd2c514b004bcf29c15f785330faf3a7f38fa0a5a7a02bcd881961c9aed

Tx prefix hash: 565e6f4ee94c23f385be223e137242d1f74b6938c4bf2f23f2f3cb276f060c96
Tx public key: c43770788ae6f57fa8faffb52433904cfcf0f753cc0d7137c58a07282576ae3c
Timestamp: 1763674628 Timestamp [UCT]: 2025-11-20 21:37:08 Age [y:d:h:m:s]: 00:032:11:27:55
Block: 1416505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23256 RingCT/type: yes/0
Extra: 01c43770788ae6f57fa8faffb52433904cfcf0f753cc0d7137c58a07282576ae3c02110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ab29cc475e3a27321706d9e4b56fcf9f325adf65a2465e648250bd8ce31e3c 0.600000000000 1905024 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": 1416515, "vin": [ { "gen": { "height": 1416505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ab29cc475e3a27321706d9e4b56fcf9f325adf65a2465e648250bd8ce31e3c" } } ], "extra": [ 1, 196, 55, 112, 120, 138, 230, 245, 127, 168, 250, 255, 181, 36, 51, 144, 76, 252, 240, 247, 83, 204, 13, 113, 55, 197, 138, 7, 40, 37, 118, 174, 60, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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