Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26d0b8c8db3d6582517d901ee7ffd99d2c7f2b7236dc30387f5f1ca7e153bbb0

Tx prefix hash: 560ab9a8c687a6bc6d1c94d8f136df0a96f87240803a0f4d17e4cbeab2ecf199
Tx public key: f8813a101c4a2958aac22b87e60e54b94b6edca1f82aecf454eef7e7e52a9b86
Timestamp: 1731281174 Timestamp [UCT]: 2024-11-10 23:26:14 Age [y:d:h:m:s]: 00:130:22:47:30
Block: 1151000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93403 RingCT/type: yes/0
Extra: 01f8813a101c4a2958aac22b87e60e54b94b6edca1f82aecf454eef7e7e52a9b8602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56fbda9b07d752a7d7ce090a5122832bdbe2c0aefc54e8acac6c0e70379595b4 0.600000000000 1636449 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": 1151010, "vin": [ { "gen": { "height": 1151000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56fbda9b07d752a7d7ce090a5122832bdbe2c0aefc54e8acac6c0e70379595b4" } } ], "extra": [ 1, 248, 129, 58, 16, 28, 74, 41, 88, 170, 194, 43, 135, 230, 14, 84, 185, 75, 110, 220, 161, 248, 42, 236, 244, 84, 238, 247, 231, 229, 42, 155, 134, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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