Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7cae619e9a582c4a817dc559983effda9e6fc71030890b4220763321e3e1468

Tx prefix hash: b49d3afdb07ff04c8415d8a2f46ea4578336f75fc2674c7fa27a490c37568521
Tx public key: 268ba4460b5e6ef4b30ba62ddf4d0c609c02862b7538b1b35ac4a9871040c78f
Timestamp: 1705244622 Timestamp [UCT]: 2024-01-14 15:03:42 Age [y:d:h:m:s]: 01:066:07:01:30
Block: 935221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308477 RingCT/type: yes/0
Extra: 01268ba4460b5e6ef4b30ba62ddf4d0c609c02862b7538b1b35ac4a9871040c78f021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 330a55d7ae09e6b365d3b3b327f5c4cd4cbc425329420dc30ce939dd076cbc70 0.600000000000 1393237 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": 935231, "vin": [ { "gen": { "height": 935221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "330a55d7ae09e6b365d3b3b327f5c4cd4cbc425329420dc30ce939dd076cbc70" } } ], "extra": [ 1, 38, 139, 164, 70, 11, 94, 110, 244, 179, 11, 166, 45, 223, 77, 12, 96, 156, 2, 134, 43, 117, 56, 177, 179, 90, 196, 169, 135, 16, 64, 199, 143, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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