Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b9fea3b55c4ecfbc3cd08724c22841e5f0330b2c3342734b5248c2d3b48ad3c

Tx prefix hash: a9e1643531103586da21136b87cc04990ac606b8a228fcc910bf5be8301214e4
Tx public key: a51b9b026b5ff257a336c813d877223030548680a0313e6f123d87d81f4351cb
Timestamp: 1754527391 Timestamp [UCT]: 2025-08-07 00:43:11 Age [y:d:h:m:s]: 00:106:02:25:19
Block: 1341807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74854 RingCT/type: yes/0
Extra: 01a51b9b026b5ff257a336c813d877223030548680a0313e6f123d87d81f4351cb021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e650241aefabbc7b21e7b8d81e8f882ba6756ca5db388a0aff2a7fe3269fd5a 0.600000000000 1829634 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": 1341817, "vin": [ { "gen": { "height": 1341807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e650241aefabbc7b21e7b8d81e8f882ba6756ca5db388a0aff2a7fe3269fd5a" } } ], "extra": [ 1, 165, 27, 155, 2, 107, 95, 242, 87, 163, 54, 200, 19, 216, 119, 34, 48, 48, 84, 134, 128, 160, 49, 62, 111, 18, 61, 135, 216, 31, 67, 81, 203, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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