Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7b1b35c283bf427afeb7aa3fde4651d37d15da8524aa0fc4ab60c86f073776

Tx prefix hash: e4c4a721fec083dfa4276d7f4cdc8328076a922dcdbf47a345b62ca44d6a2e4d
Tx public key: 75a5c2d761f99b7305984e98e07e285a002224316fdda1ac63d7eb37d0acda93
Timestamp: 1750835990 Timestamp [UCT]: 2025-06-25 07:19:50 Age [y:d:h:m:s]: 00:142:03:26:32
Block: 1312364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99529 RingCT/type: yes/0
Extra: 0175a5c2d761f99b7305984e98e07e285a002224316fdda1ac63d7eb37d0acda93021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ab7e0ed2485bfd6c44ea20660000d4c3931dba14779fd2602fa26b5658483a3 0.600000000000 1799997 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": 1312374, "vin": [ { "gen": { "height": 1312364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ab7e0ed2485bfd6c44ea20660000d4c3931dba14779fd2602fa26b5658483a3" } } ], "extra": [ 1, 117, 165, 194, 215, 97, 249, 155, 115, 5, 152, 78, 152, 224, 126, 40, 90, 0, 34, 36, 49, 111, 221, 161, 172, 99, 215, 235, 55, 208, 172, 218, 147, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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