Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b56bd7c8917f2edc1825c9619e4a08ded67424ef819c771a9079d82c07f446

Tx prefix hash: 282aee23978a8f9c741fb5342331dfc34691079f4afc8dfd7cf44c7208bde493
Tx public key: decf76c64208046803adb083a532cc4c4aa929b38905d2b908435aa284304c5d
Timestamp: 1729361371 Timestamp [UCT]: 2024-10-19 18:09:31 Age [y:d:h:m:s]: 00:217:00:55:52
Block: 1135155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154931 RingCT/type: yes/0
Extra: 01decf76c64208046803adb083a532cc4c4aa929b38905d2b908435aa284304c5d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27fc8bbf6c0f32b68865ae2144e436137bc7a6d7143e91acbe81ae943fa47593 0.600000000000 1618486 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": 1135165, "vin": [ { "gen": { "height": 1135155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27fc8bbf6c0f32b68865ae2144e436137bc7a6d7143e91acbe81ae943fa47593" } } ], "extra": [ 1, 222, 207, 118, 198, 66, 8, 4, 104, 3, 173, 176, 131, 165, 50, 204, 76, 74, 169, 41, 179, 137, 5, 210, 185, 8, 67, 90, 162, 132, 48, 76, 93, 2, 17, 0, 0, 0, 2, 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