Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041beb7d7d81685e224c45c55636a37f514a40480c36e17778451a2ab6758d7c

Tx prefix hash: d9a86b96522e647fccb3cc878a5c0da6f038cd0fc139e6348afa28c104414cbc
Tx public key: 10ab8c9cf29818d4c1f08e05cc4d91de15f7b37f189812256e0e8c3a37cf4e40
Timestamp: 1754475017 Timestamp [UCT]: 2025-08-06 10:10:17 Age [y:d:h:m:s]: 00:107:14:16:24
Block: 1341405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75902 RingCT/type: yes/0
Extra: 0110ab8c9cf29818d4c1f08e05cc4d91de15f7b37f189812256e0e8c3a37cf4e40021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58ef5b32040a3894102c582ddd8e8be5fcd61570b81c30196310d0129d9b4ec6 0.600000000000 1829230 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": 1341415, "vin": [ { "gen": { "height": 1341405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58ef5b32040a3894102c582ddd8e8be5fcd61570b81c30196310d0129d9b4ec6" } } ], "extra": [ 1, 16, 171, 140, 156, 242, 152, 24, 212, 193, 240, 142, 5, 204, 77, 145, 222, 21, 247, 179, 127, 24, 152, 18, 37, 110, 14, 140, 58, 55, 207, 78, 64, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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