Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433ecfd6c7036ec876a0016cb6f577ca7c0516a25ef9d8a5091714c49621b26a

Tx prefix hash: f5006a8b39d1871a75d6a5f2280f6b91e9de2b42e6184d57ad3170d76edec44a
Tx public key: f99d3a3e308ce502db7c6c0b4aaabf805f16b570c84ec46ed082299a1eb535ad
Timestamp: 1741620621 Timestamp [UCT]: 2025-03-10 15:30:21 Age [y:d:h:m:s]: 00:246:17:44:52
Block: 1236346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174064 RingCT/type: yes/0
Extra: 01f99d3a3e308ce502db7c6c0b4aaabf805f16b570c84ec46ed082299a1eb535ad02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c2ef50d2433ef103aa6d11a5e6a042d0e7a792883645086c05ed7d845440885 0.600000000000 1723293 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": 1236356, "vin": [ { "gen": { "height": 1236346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c2ef50d2433ef103aa6d11a5e6a042d0e7a792883645086c05ed7d845440885" } } ], "extra": [ 1, 249, 157, 58, 62, 48, 140, 229, 2, 219, 124, 108, 11, 74, 170, 191, 128, 95, 22, 181, 112, 200, 78, 196, 110, 208, 130, 41, 154, 30, 181, 53, 173, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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