Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f3990df230c697044c3c9c58c96d7ede4406888af9446e6b72dc9fde6bc973

Tx prefix hash: e73c4bf0abe8b215158ad241298461fa7c6b6b2a9c79503b02ac0f46cdd577c7
Tx public key: 0ea4d69f28ac8d79d7f962984c012776171c0793317e2466bbdfa15855b8824e
Timestamp: 1745004073 Timestamp [UCT]: 2025-04-18 19:21:13 Age [y:d:h:m:s]: 00:223:11:52:29
Block: 1264349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157462 RingCT/type: yes/0
Extra: 010ea4d69f28ac8d79d7f962984c012776171c0793317e2466bbdfa15855b8824e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaae5e284db40936a707978456fcb27d80fbb5a10a60ccae1fd5d9b954b5c7be 0.600000000000 1751546 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": 1264359, "vin": [ { "gen": { "height": 1264349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaae5e284db40936a707978456fcb27d80fbb5a10a60ccae1fd5d9b954b5c7be" } } ], "extra": [ 1, 14, 164, 214, 159, 40, 172, 141, 121, 215, 249, 98, 152, 76, 1, 39, 118, 23, 28, 7, 147, 49, 126, 36, 102, 187, 223, 161, 88, 85, 184, 130, 78, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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