Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df791f2111e87d9ff9024bc7c78d8c5cad642b646cb18bbff8520fd338f77c7

Tx prefix hash: a3e29cab014cf4814b96435172922f4bae23ef074190d41f1f3005f4213a4c20
Tx public key: 70b2cc1229ad23ed153d362b3cbad9b9f07238d61b5d74d9760d7ae5b2bdbce2
Timestamp: 1735778196 Timestamp [UCT]: 2025-01-02 00:36:36 Age [y:d:h:m:s]: 00:323:18:28:22
Block: 1188229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228919 RingCT/type: yes/0
Extra: 0170b2cc1229ad23ed153d362b3cbad9b9f07238d61b5d74d9760d7ae5b2bdbce2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8df603c2e1ab45cdf95402df2e8953cc5c8eb4b8c947dc75d5551f6236e4daea 0.600000000000 1674730 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": 1188239, "vin": [ { "gen": { "height": 1188229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8df603c2e1ab45cdf95402df2e8953cc5c8eb4b8c947dc75d5551f6236e4daea" } } ], "extra": [ 1, 112, 178, 204, 18, 41, 173, 35, 237, 21, 61, 54, 43, 60, 186, 217, 185, 240, 114, 56, 214, 27, 93, 116, 217, 118, 13, 122, 229, 178, 189, 188, 226, 2, 17, 0, 0, 0, 5, 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