Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24b4e0ef32d8e3ed0205bad58ca510e8cf990045701598716babfcbe989a4fff

Tx prefix hash: f0d194d4eac51597f2740a171f842f38d4a52b7a4d2e5a8b16e1b72b0c1df728
Tx public key: 1e6f2be188d38b073c58dc765e9c394e455ae35d983b9e079409eafc4fa22e55
Timestamp: 1722322217 Timestamp [UCT]: 2024-07-30 06:50:17 Age [y:d:h:m:s]: 00:275:03:39:47
Block: 1076808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196563 RingCT/type: yes/0
Extra: 011e6f2be188d38b073c58dc765e9c394e455ae35d983b9e079409eafc4fa22e5502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 503a5602c0fe10e2aa189c0fb2b027f25121580a965a894e96c853e6b12cef13 0.600000000000 1549349 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": 1076818, "vin": [ { "gen": { "height": 1076808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "503a5602c0fe10e2aa189c0fb2b027f25121580a965a894e96c853e6b12cef13" } } ], "extra": [ 1, 30, 111, 43, 225, 136, 211, 139, 7, 60, 88, 220, 118, 94, 156, 57, 78, 69, 90, 227, 93, 152, 59, 158, 7, 148, 9, 234, 252, 79, 162, 46, 85, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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