Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1044903dbb0d7e3ad6e0ab91bc8ceddbf7ef6702439915daa515dddef709304

Tx prefix hash: eb70f9547b51805602562d17b7637cc0672ec7d24eb918d059256aa4a6189a95
Tx public key: 0adcecf35c9df9e438a244973fa1bbf03f352fd6c906c9e909af716ae040ce3c
Timestamp: 1745408708 Timestamp [UCT]: 2025-04-23 11:45:08 Age [y:d:h:m:s]: 00:212:02:23:30
Block: 1267687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149308 RingCT/type: yes/0
Extra: 010adcecf35c9df9e438a244973fa1bbf03f352fd6c906c9e909af716ae040ce3c021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe658623921ed65f9aa06b1b47b003ea70477d20f77749f87131bfc9902b25e 0.600000000000 1754916 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": 1267697, "vin": [ { "gen": { "height": 1267687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe658623921ed65f9aa06b1b47b003ea70477d20f77749f87131bfc9902b25e" } } ], "extra": [ 1, 10, 220, 236, 243, 92, 157, 249, 228, 56, 162, 68, 151, 63, 161, 187, 240, 63, 53, 47, 214, 201, 6, 201, 233, 9, 175, 113, 106, 224, 64, 206, 60, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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