Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033d03c5dbc24b0e2f91abc25beb1d90ca054c111874a1600018618381c2b44b

Tx prefix hash: 8ee7ab3cc5c6b8d923a7169fb41e4b3588a5704470959450dc5c85ee3869863f
Tx public key: cf1ddd0f1ca9c3d17827460243728664e41045f9d0f2dda331bcedea6a952fbe
Timestamp: 1711994217 Timestamp [UCT]: 2024-04-01 17:56:57 Age [y:d:h:m:s]: 01:045:14:06:11
Block: 991155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293596 RingCT/type: yes/0
Extra: 01cf1ddd0f1ca9c3d17827460243728664e41045f9d0f2dda331bcedea6a952fbe0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3778e010afd7fa391bece037140a70a5a4642bf4f1a5b5e15f5e30112745c645 0.600000000000 1451489 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": 991165, "vin": [ { "gen": { "height": 991155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3778e010afd7fa391bece037140a70a5a4642bf4f1a5b5e15f5e30112745c645" } } ], "extra": [ 1, 207, 29, 221, 15, 28, 169, 195, 209, 120, 39, 70, 2, 67, 114, 134, 100, 228, 16, 69, 249, 208, 242, 221, 163, 49, 188, 237, 234, 106, 149, 47, 190, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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