Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f29cd2b18c957113aabdb8cdf77596fc83930a6a4310027e7a123779ba7c0f60

Tx prefix hash: 3099cb3e9552714d0b95315740da6f3adf41bec882114736b2b329a1cc774b09
Tx public key: e871e992cf786a8f2a78ed7e526bd044c001308fa37eaff59aa3149a6c497a7a
Timestamp: 1717477624 Timestamp [UCT]: 2024-06-04 05:07:04 Age [y:d:h:m:s]: 00:303:12:56:10
Block: 1036658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216905 RingCT/type: yes/0
Extra: 01e871e992cf786a8f2a78ed7e526bd044c001308fa37eaff59aa3149a6c497a7a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907aafb83a2ff2a09ad452f8f36bcd59541aa1cac088b02ad84ff81d5fc3a43d 0.600000000000 1505187 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": 1036668, "vin": [ { "gen": { "height": 1036658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907aafb83a2ff2a09ad452f8f36bcd59541aa1cac088b02ad84ff81d5fc3a43d" } } ], "extra": [ 1, 232, 113, 233, 146, 207, 120, 106, 143, 42, 120, 237, 126, 82, 107, 208, 68, 192, 1, 48, 143, 163, 126, 175, 245, 154, 163, 20, 154, 108, 73, 122, 122, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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