Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92456d31114bc72923e770b8a292c6255806adb1e4d310245e96eceb287a0e05

Tx prefix hash: 994702c5d53d17fa5bb8d6e9a3d2520906159075c75a6537725a2e1727cd4cc9
Tx public key: 0069f8d8a40b1292ed27e8066097f723ac6b01206f314fa465c02d4ce28c265a
Timestamp: 1730148392 Timestamp [UCT]: 2024-10-28 20:46:32 Age [y:d:h:m:s]: 00:148:16:32:59
Block: 1141625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106079 RingCT/type: yes/0
Extra: 010069f8d8a40b1292ed27e8066097f723ac6b01206f314fa465c02d4ce28c265a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b3fc00b7c9f5cfc0c43c015ac5a952acad8c7fc10ab51973e1ac1065a004e4 0.600000000000 1625434 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": 1141635, "vin": [ { "gen": { "height": 1141625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b3fc00b7c9f5cfc0c43c015ac5a952acad8c7fc10ab51973e1ac1065a004e4" } } ], "extra": [ 1, 0, 105, 248, 216, 164, 11, 18, 146, 237, 39, 232, 6, 96, 151, 247, 35, 172, 107, 1, 32, 111, 49, 79, 164, 101, 192, 45, 76, 226, 140, 38, 90, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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